Update Agent
Agents
Update Agent
Update agent metadata and optionally reprovision
PATCH
Update Agent
Updates an existing agent’s configuration. Changes to templates or configuration can trigger reprovisioning on the gateway.
Authentication
Requires organization admin authentication viaAuthorization: Bearer <token> header.
Path Parameters
Agent UUID or ID to update
Query Parameters
Force reprovisioning even if no significant changes detected
Request Body
All fields are optional. Only include fields you want to update.New display name for the agent
Move agent to a different board (requires appropriate permissions)
Designate this agent as the gateway main agent
Update lifecycle status:
active, paused, retiredUpdate heartbeat policy
Update identity profile values
Replace identity template (triggers reprovisioning)Example: “Focus on root cause analysis first.”
Replace soul template (triggers reprovisioning)Example: “Escalate only after checking all known mitigations.”
Response
Returns an updatedAgentRead object with the same structure as List Agents.
Reprovisioning Triggers
Updating these fields will trigger reprovisioning:identity_templatesoul_templateboard_id(if moving to a different board)
Example Request
Example Response
Error Responses
403 Forbidden
Insufficient permissions to update this agent
404 Not Found
Agent ID does not exist or is not accessible
422 Unprocessable Entity
Validation failed (e.g., invalid status value)
502 Bad Gateway
Gateway RPC call failed during reprovisioning
Use Cases
- Pause Agent: Set
status: "paused"to temporarily disable an agent - Update Instructions: Change templates to adjust agent behavior
- Move Agent: Reassign agent to a different board
- Update Profile: Add metadata for routing decisions